---

This section details on the original issue you should resolve

<issue_title>Shared Global Enforcer state breaks Async tests</issue_title>
<issue_description>## Problem
When using EnforcerServer with a named enforcer (e.g., "reach_enforcer"), all tests share the same global state, making async: true tests fail with race conditions.

What Happened

# This fails with async: true
defmodule Reach.Casbin.AclTest do
  use Reach.CasbinCase, async: true  # ❌ Tests interfere with each other
  
  test "admin has permissions" do
    create_test_policies(test_org_id)  # Adds policies
    # Another test's cleanup deletes these policies mid-test!
    assert Acl.allow?(...) # Returns false unexpectedly
  end
end

Symptoms

• Policies.list() returns [] even after adding policies
• add_policy returns {:error, :already_existed} but policies aren't in memory
• Tests pass individually but fail when run together

Root Cause

# All tests use the same enforcer instance
@enforcer_name "reach_enforcer"
EnforcerServer.add_policy(@enforcer_name, ...)

One test's on_exit cleanup deletes policies while another test is running.

Workaround

# Must disable async
defmodule Reach.Casbin.AclTest do
  use Reach.CasbinCase  # Removed: async: true
end

Proposed Solutions

1. Support dynamic enforcer names per test
2. Provide enforcer isolation/sandboxing for tests
3. Document the async limitation</issue_description>

Comments on the Issue (you are @copilot in this section)